Upgrade ESLint and dependencies, fix new lint errors, switch Travis to Yarn#8309
Merged
tomocchino merged 4 commits intofacebook:masterfrom Nov 17, 2016
Merged
Upgrade ESLint and dependencies, fix new lint errors, switch Travis to Yarn#8309tomocchino merged 4 commits intofacebook:masterfrom
tomocchino merged 4 commits intofacebook:masterfrom
Conversation
tomocchino
force-pushed
the
fix-lint-and-yarn
branch
2 times, most recently
from
02c3447 to
b03ad31
Compare
tomocchino
changed the title
tomocchino
force-pushed
the
fix-lint-and-yarn
branch
from
c3fda1f to
dbd1f10
Compare
zpao
approved these changes
Nov 17, 2016
| } | ||
|
|
||
| toJSON(): ReactTestRendererJSON { | ||
| // not using `children`, but I don't wanna rewrite without destructuring |
tomocchino
force-pushed
the
fix-lint-and-yarn
branch
from
dbd1f10 to
bdd49c4
Compare
Also pull in fbjs for extending properly, per @zpao. This also disables consistent-return, which has about 80 failing cases in React currently. If we'd like to turn this back on, we should do it separately and fix all the call sites properly (rather than just adding 'return undefined;' everywhere, which adds no value. Fixes to all existing lint errors plus an update for yarn.lock to follow.
Unfortunately I had to add three eslint-disable-next-line instances. All have explanations inline.
tomocchino
force-pushed
the
fix-lint-and-yarn
branch
from
bdd49c4 to
64ce048
Compare
Collaborator
|
Tagging as patch because it also happens to fix an issue for Rollup users. (#8318) |
Member
|
I haven't tried but this might be pretty tough to cherry-pick in a patch, perhaps even a minor. It might be worthwhile to just take the specific changes in the branch. |
Collaborator
|
k, I'll cherry-pick it |
jackjocross
added a commit
to jackjocross/react
that referenced
this pull request
Jan 13, 2017
…o Yarn (facebook#8309) * Update ESLint to 3.10.2 Also pull in fbjs for extending properly, per @zpao. This also disables consistent-return, which has about 80 failing cases in React currently. If we'd like to turn this back on, we should do it separately and fix all the call sites properly (rather than just adding 'return undefined;' everywhere, which adds no value. Fixes to all existing lint errors plus an update for yarn.lock to follow. * Update yarn.lock after the eslint update. * Fix all new eslint failures Unfortunately I had to add three eslint-disable-next-line instances. All have explanations inline. * Switch Travis to use yarn instead of npm
gaearon
pushed a commit
that referenced
this pull request
Jan 23, 2017
* devDependencies: add core-js and es6-symbol polyfill for tests * Update Flow and fix issues (#8006) * Add npm v4.0.0 support (#8082) * Add support for node v7 (#8135) * Upgrade ESLint and dependencies, fix new lint errors, switch Travis to Yarn (#8309) * Update ESLint to 3.10.2 Also pull in fbjs for extending properly, per @zpao. This also disables consistent-return, which has about 80 failing cases in React currently. If we'd like to turn this back on, we should do it separately and fix all the call sites properly (rather than just adding 'return undefined;' everywhere, which adds no value. Fixes to all existing lint errors plus an update for yarn.lock to follow. * Update yarn.lock after the eslint update. * Fix all new eslint failures Unfortunately I had to add three eslint-disable-next-line instances. All have explanations inline. * Switch Travis to use yarn instead of npm * Update all Jest packages to 17.x (#8327) * Update all Jest packages to 17.x, cache babel-jest transforms * Remove the caching Looking at the other builds it doesn't seem to actually be that necessary. The bottleneck is executors, not build time. * Remove unnecessary package, fix fiber test runner * Regenerate yarn lockfile * Update Flow to 0.37.0 (#8608) Nothing really changes. * Update to Jest 18 (#8621) * mockImpl -> mockImplementation D4329549 * Fixed linting errors * circle.yml and circleci scripts * Update Flow and fix issues (#8006) * Fixed flow errors * Updated shrinkwrap * Removed unnecessary change * Added jest --runInBand flag * Removed ReactDOMFiber changes
gaearon
pushed a commit
that referenced
this pull request
Jan 23, 2017
* devDependencies: add core-js and es6-symbol polyfill for tests * Update Flow and fix issues (#8006) * Add npm v4.0.0 support (#8082) * Add support for node v7 (#8135) * Upgrade ESLint and dependencies, fix new lint errors, switch Travis to Yarn (#8309) * Update ESLint to 3.10.2 Also pull in fbjs for extending properly, per @zpao. This also disables consistent-return, which has about 80 failing cases in React currently. If we'd like to turn this back on, we should do it separately and fix all the call sites properly (rather than just adding 'return undefined;' everywhere, which adds no value. Fixes to all existing lint errors plus an update for yarn.lock to follow. * Update yarn.lock after the eslint update. * Fix all new eslint failures Unfortunately I had to add three eslint-disable-next-line instances. All have explanations inline. * Switch Travis to use yarn instead of npm * Update all Jest packages to 17.x (#8327) * Update all Jest packages to 17.x, cache babel-jest transforms * Remove the caching Looking at the other builds it doesn't seem to actually be that necessary. The bottleneck is executors, not build time. * Remove unnecessary package, fix fiber test runner * Regenerate yarn lockfile * Update Flow to 0.37.0 (#8608) Nothing really changes. * Update to Jest 18 (#8621) * mockImpl -> mockImplementation D4329549 * Fixed linting errors * circle.yml and circleci scripts * Update Flow and fix issues (#8006) * Fixed flow errors * Updated shrinkwrap * Removed unnecessary change * Added jest --runInBand flag * Removed ReactDOMFiber changes
acusti
pushed a commit
to brandcast/react
that referenced
this pull request
Mar 15, 2017
…o Yarn (facebook#8309) * Update ESLint to 3.10.2 Also pull in fbjs for extending properly, per @zpao. This also disables consistent-return, which has about 80 failing cases in React currently. If we'd like to turn this back on, we should do it separately and fix all the call sites properly (rather than just adding 'return undefined;' everywhere, which adds no value. Fixes to all existing lint errors plus an update for yarn.lock to follow. * Update yarn.lock after the eslint update. * Fix all new eslint failures Unfortunately I had to add three eslint-disable-next-line instances. All have explanations inline. * Switch Travis to use yarn instead of npm
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Test Plan: yarn run lint, yarn run test, flow, everything is clean
This also involved pulling in the latest fbjs so we can extend that .eslintrc.js. One goal here is to be able to use yarn exclusively in Travis / CircleCI.
As a followup, I can try to add a custom rule to turn the ESLint
strictrule back on, because we need to deal with the fact that ESLint thinksimport typeFlow statements are module imports.Sorry this is doing so much, but these are all pretty interconnected. Let me know if you want me to split this into multiple PRs somehow.